AddOrEditSDI
Description:
Edits SDIs or adds them if they do not exist and SDI and returns their identifiers.
Input Properties
sdcid
Description:
Identifier of the SDC.
Required:
Yes
keyid1
Description:
Identifiers of the SDIs.
Required:
Yes
keyid2
Description:
Identifiers of the SDIs.
Required:
Only for multi-key SDCs.
keyid3
Description:
Identifiers of the SDIs.
Required:
Only for multi-key SDCs.
auditreason
Description:
Auditing information recorded in the "Reason" column of the TraceLog table.
Required:
No
auditactivity
Description:
Auditing information recorded in the "Activity" column of the TraceLog table.
Required:
No
auditsignedflag
Description:
Auditing information recorded in the "SignedFlag" column of the TraceLog table.
Required:
No
auditdt
Description:
Auditing information recorded in the "ModDt" column of the TraceLog table.
Required:
No
eventnotify
Description:
Determines whether or not (Y/N) an EventNotify Action is posted onto the ToDo List when this Action executes.
Deprecated:
As of version 7, Event Notify actions are no longer generated
templateid
Description:
Identifier of a single-key SDI Template.
Required:
Only if the new SDIs are based on a single-key SDI Template.
templatekeyid1
Description:
Identifier of a multi-key SDI Template.
Required:
Only if the new SDIs are based on a multi-key SDI Template.
Comments:
  • If you enable Automatic Key Generation (using the overrideautokey property) and do not specify keyid1, keyid2, and keyid3, the keys are automatically generated.
  • If the SDI Template has User Roles and Role Level Access is enabled, the Roles are added to the new SDIs.
templatekeyid2
Description:
Identifier of a multi-key SDI Template.
Required:
Only if the new SDIs are based on a multi-key SDI Template.
Comments:
  • If you enable Automatic Key Generation (using the overrideautokey property) and do not specify keyid1, keyid2, and keyid3, the keys are automatically generated.
  • If the SDI Template has User Roles and Role Level Access is enabled, the Roles are added to the new SDIs.
templatekeyid3
Description:
Identifier of a multi-key SDI Template.
Required:
Only if the new SDIs are based on a multi-key SDI Template.
Comments:
  • If you enable Automatic Key Generation (using the overrideautokey property) and do not specify keyid1, keyid2, and keyid3, the keys are automatically generated.
  • If the SDI Template has User Roles and Role Level Access is enabled, the Roles are added to the new SDIs.
templateflag
Description:
Determines whether or not (Y/N) new SDIs are created as SDI Templates.
Required:
Only if new SDIs are created as SDI Templates.
adduserroles
Description:
Grants/blocks (Y/N) SDI access for all Roles assigned to the current user.
Required:
No
Comments:
  • Do not use this property if the new SDIs are based on an existing SDI Template. In this case, use the addtemplateroles property.
  • Role-Level Access must be enabled for the SDC.
  • Use this property only in a JSP, as the JSP can pass the connectionid to the Action (thereby identifying the current user).
addtemplateroles
Description:
Grants/blocks (Y/N) SDI access for all Roles assigned to the current user.
Required:
No
Comments:
  • Use this property only if the new SDIs are based on an existing SDI Template.
  • Role-Level Access must be enabled for the SDC.
  • Use this property only in a JSP, as the JSP can pass the connectionid to the Action (thereby identifying the current user).
usetemplatedepartment
Description:
If Departmental Security is enabled for the SDC, the new SDI is created with the SecurityDepartment and SecurityUser columns. The AddSDI Action automatically populates these columns as follows:
  • If you pass values to either (or both) of these columns, the values are used and can be modified by the EditSDI Action.
  • If you do not pass a value to the SecurityUser column, it is popluated with the current user.
  • If the SDI you are creating is based on an existing SDI Template (using the SDI Template property), and the SDI Template has a SecurityDepartment column, the usetemplatedepartment property behaves in this manner:
    • Y copies the SecurityDepartment value from the SDI Template to the newly created SDI.
    • N (default) copies the current user's Default Department to the newly created SDI.
Required:
No
applyworkitems
Description:
If the Template Flag property is set to Yes (Y), this automatically applies Workitems from the Sample Template.
Required:
No
forcenew
Description:
Determines whether or not a new Data Set is added when Template Workitems are applied. This overrides the Workitem definition:
  • Y enables the "Force New" option for Workitems, and overrides the "Force New" setting in the Workitem Maintenance Page. When adding Workitems to this SDI, enabling the "Force New" option always creates a new dataset. This will let you resolve Data Sets after you have deleted the Workitem, as each Workitem Item will be uniquely identified.
  • N uses the "Force New" setting in the Workitem Maintenance Page.
Required:
No
applylock
Description:
Determines whether or not (Y/N) data are locked during Action processing.
Required:
No
ignoreedits
Description:
For Internal use only
alternatekeycolumns
Description:
List of alternate key columns
Output Properties
newkeyid1
Description:
List of newly created SDI's keyid1
newkeyid2
Description:
List of newly created SDI's keyid2
newkeyid3
Description:
List of newly created SDI's keyid3
Additional Information
Copyright © 1999-2016 LABVANTAGE Solutions, Inc.